Safety integrated shared vehicle system and methods

ABSTRACT

A SIPV system comprising: a SIPV network connecting to at least a SIPV that is available for rental where an integrated safety control apparatus is operably connected to a safety device mounted on the SIPV and upon rental of the SIPV, the safety device is deployed for use from the SIPV.

CLAIM OF PRIORITY

This patent application claims the benefit of priority of Viner, et.al,U.S. Provisional Patent Application Ser. No. 62/820,005 filed on Mar.18, 2019 (Attorney Docket No. 5148.001PRV), the benefit of priority ofViner, et.al, U.S. Provisional Patent Application Ser. No. 62/820,013filed on Mar. 18, 2019 (Attorney Docket No. 5148.002PRV), the benefit ofpriority of Viner, et.al, U.S. Provisional Patent Application Ser. No.62/820,039 filed on Mar. 18, 2019 (Attorney Docket No. 5148.003PRV), thebenefit of priority of Viner, et.al, U.S. Provisional Patent ApplicationSer. No. 62/875,187 filed on Jul. 17, 2019 (Attorney Docket No.5148.004PRV), and the benefit of priority of Viner, et.al, U.S.Provisional Patent Application Ser. No. 62/909,653 filed on Oct. 2, 2019(Attorney Docket No. 5148.013PRV), all of which are hereby incorporatedby reference herein in their entireties.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever. The following notice applies to the software and dataas described below and in the drawings that form a part of thisdocument: Copyright ©2019-2020 Wheels Inc. All Rights Reserved.

Personal Mobility Vehicle” filed on Oct. 3, 2019 (Attorney Docket No.5148.013PRV), which is hereby incorporated by reference herein in itsentirety.

BACKGROUND

The shared vehicle ecosystem has moved from a nascent set of startupcompanies to a vibrant industry with a number of companies in a largenumber of markets, each company specializing in short distance rentalsof bicycles and powered scooters. The industry has also experiencedgrowing pains in the areas of safety. There have been a number of highlypublicized accidents, injuries and deaths of subscribers to theseservices. Several safety measures have been fielded including rental ofsafety devices (e.g. traditional bicycle helmets rented or variousdisposable helmet types). In each case, these half measures have leftmuch to be desired in the areas of helmet sanitation, item loss/theftand validation that the safety device is being used and were ultimatelyunsuccessful commercially. Additionally, there has been no methodologyattached to the shared ride systems deployed that will actively create asafer ride for the rider. In all previous cases, the safety device isnot in communication with the shared vehicle, not integrated to thedeployment or recovery of the safety device before and after the sharedvehicle rental. Additionally, each shared vehicle is not in activecommunication with the shared ride provisioning system to monitor ridesand riders for safety related behaviors. Additionally, all of theprevious safety devices also rely heavily on a direct human involvement(helmet rental/recovery by a human) (sanitation and restocking by ahuman) and there was virtually no ability to prevent a rider fromignoring the use of a safety device.

SUMMARY

The present inventors have recognized, among other things, that aproblem to be solved can include minimizing the labor involved indeploying safety devices with a shared ride system. Another aspect ofthe problem solved is the integration of safety system, sensors and usersafety devices into the actual design of the personal mobility vehicle.Another aspect of the problem solved is the ongoing upkeep andmaintenance of personal mobility vehicles (shared vehicles) by webenabled servicing of the invention. A third aspect of the problem solvedis the integration of service items with the integral safety sensors andinterconnects in the described solution. A fourth aspect of the problemsolved is the closed loop monitoring of safety protocols from sensors inthe personal mobility vehicle components, the safety equipment worn bythe user, mobile devices of the user, and the vehiclemanagement/servicing protocols.

The present subject matter provides a solution to these problems, suchas by using integrally designed safety devices associated or integratedwith a personal mobility vehicle that a) are deployed within the sharedvehicle, b) are communicatively coupled to the vehicle, c) coupled tothe system as a whole, which is in constant communication between thevehicle, the shared vehicle management system, and the various safetydevices, thereby integrating safety and serviceability in the design ofthe shared vehicle. that interacts with the user who is using thevarious safety checks during a ride, d) the retrieval of any deployeduser safety devices, and e) the verified sanitation of any deployed usersafety devices, and f) the reset of any user safety device to be readyfor the next user. By accomplishing these integrations, the presentsolution comprises a number of aspects where the solution can jointlyvalidate a user to use the personal mobility vehicle, deploy thepersonal mobility vehicle, manage the deployment of a wearable usersafety devices at the time of rental, validate the use of the helmet,monitor the use of a helmet by a shared vehicle renter during therental, monitor the personal mobility vehicle during the rental, and theretrieval and sanitization of the helmet without the intervention of aservicing personnel allowing the immediate redeployment of the sharedvehicle with the same wearable safety device, as well as detectingwhether a user is safely using the shared vehicle. The present solutioncan additionally monitor the safety state of a user during a ride by useof additional sensors on the personal mobility vehicle.

Each of these non-limiting examples can stand on its own or can becombined in various permutations or combinations with one or more of theother examples.

This overview is intended to provide an overview of subject matter ofthe present patent application. It is not intended to provide anexclusive or exhaustive explanation of the invention. The detaileddescription is included to provide further information about the presentpatent application.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

To easily identify the discussion of any particular element or act, themost significant digit or digits in a reference number refer to thefigure number in which that element is first introduced.

In the drawings, which are not necessarily drawn to scale, like numeralsmay describe similar components in different views. Like numerals havingdifferent letter suffixes may represent different instances of similarcomponents. The drawings illustrate generally, by way of example, butnot by way of limitation, various embodiments discussed in the presentdocument.

FIG. 1 is a diagrammatic representation of a networked environment inwhich the present disclosure may be deployed, in accordance with someexample embodiments.

FIG. 2 is a diagrammatic representation of a processing environment, inaccordance with some example embodiments.

FIG. 3 is block diagram showing a software architecture within which thepresent disclosure may be implemented, according to an exampleembodiment,

FIG. 4 is a diagrammatic representation of a machine in the form of acomputer system within which a set of instructions may be executed forcausing the machine to perform any one or more of the methodologiesdiscussed herein, in accordance with some example embodiments.

FIG. 5 illustrates a SIPV system and its functional architecture inaccordance with one embodiment.

FIG. 6 illustrates a Meshed SIPV Network in accordance with oneembodiment.

FIG. 7 is an example of a safety integrated electric vehicle disclosedherein;

FIG. 8 is a cutaway of the safety integrated electric vehicle disclosedherein, showing the user control interfaces;

FIG. 9 is a cutaway of the safety integrated electric vehicle disclosedherein, showing mechanical and system components;

FIG. 10 is a cutaway of the safety integrated electric vehicle disclosedherein, showing helmet and system interactions as well as other vehiclecomponents;

FIG. 11 is a cutaway of the safety integrated electric vehicle disclosedherein, showing electronic and sensor safety features;

FIG. 12 illustrates a Deployable Safety Device Assembly in accordancewith one embodiment;

FIG. 13 illustrates an Initiation of SIPV ride in accordance with oneembodiment; and

FIG. 14 illustrates a safety process during SIPV rental in accordancewith one embodiment.

DETAILED DESCRIPTION System Level Description:

The example used in this description is intended as a median example ofthe solution proposed, rather than an exhaustive example of everypermutation of this proposed solution. It can be appreciated that therecombination of the various aspects of this solution may result in manypermutations.

FIG. 1 is a diagrammatic representation of a SIPV networked computingenvironment 100 in which some example variations of the present solutionmay be implemented or deployed.

One or more SIPV system application servers 104 provide server-sidefunctionality via a network 102 to a networked user device, in the formof a user client device 106 that is accessed by a SIPV user 128. A webclient 110 (e.g., a browser) and a programmatic client 108 (e.g., an“app”) are hosted and execute on the web client 110 to allow the SIPVuser 128 to purchase a SIPV 700 ride.

An Application Program Interface (API) server 118 and a web server 120provide respective programmatic and web interfaces to SIPV systemapplication servers 104. A specific application server 116 hosts a SIPVSystem Code 122, which includes components, modules and/or applicationsas discussed earlier.

The web client 110 communicates with the SIPV System Code 122 via theweb interface supported by the web server 120. Similarly, theprogrammatic client 108 communicates with the SIPV System Code 122 viathe programmatic interface provided by the Application Program Interface(API) server 118. The third-party application 114 may, for example, be aGoogle Maps, Paypal or other commonly used apps to assist the SIPV user128 in their purchase.

The application server 116 is shown to be communicatively coupled todatabase servers 124 that facilitates access to an information storagerepository or databases 126. In an example embodiment, the databases 126includes storage devices that store information to be published and/orprocessed by the SIPV System Code 122. (e.g. Rider data, prior usehistory and other data that assists the execution of the SIPV 700experience.

Additionally, a third-party application 114 executing on a third-partyserver 112, is shown as having programmatic access to the applicationserver 116 via the programmatic interface provided by the ApplicationProgram Interface (API) server 118. For example, the third-partyapplication 114, using information retrieved from the application server116, may support one or more features or functions on a website hostedby the third party. (e.g., SIPV user 128 present location, credit check,credit card transactions)

Turning now to FIG. 2, a diagrammatic representation of a the SIPVprocessing environment 200 is shown, which includes the onboard computer808 further comprising Communication Processor 206, the Power ManagementPower Processor 208, and a Main Processor 202 (e.g., a GPU, CPU orcombination thereof).

The Main Processor 202 is shown to be coupled to a power source 204, andto include (either permanently configured or temporarily instantiated)modules, namely a Safety component 210, a Monitoring component 212, andan Operations component 214. The Safety component 210 operationallygenerates all safety related interconnections between the SIPV 700 andits SIPV sensors 508, the Monitoring component 212 operationallygenerates all other monitoring tasks including monitoring commands orrequests from the SIPV system 500 or requests from the present userdevices, and the Operations component 214 operationally generates allbasic functions and operations of the SIPV not related to maintainingsafety or monitoring tasks, this comprises additional tasks likemaintenance, system or sensor availability as well as alerting to theother processors as the Operations component 214 detects a new orprojected servicing condition. As illustrated, the Main Processor 202 iscommunicatively coupled to both the Communication Processor 206 andPower Processor 208, and receives all external SIPV 700communications/requests from the Communication Processor 206, as well aspower status, power source status and charge condition from the PowerProcessor 208.

FIG. 3 is a general SIPV 700 block diagram 300 illustrating a softwarearchitecture 304, which can be installed on any one or more of thedevices described herein. The software architecture 304 is supported byhardware such as a machine 302 that includes processors 320, memory 326,and I/O components 338. In this example, the software architecture 304can be conceptualized as a stack of layers, where each layer provides aparticular functionality. The software architecture 304 includes layerssuch as an operating system 312, libraries 310, frameworks 308, and SIPVapplications 306. Operationally, the SIPV applications 306 invoke APIcalls 350 through the software stack and receive messages 352 inresponse to the API calls 350.

The operating system 312 manages hardware resources and provides commonservices. The operating system 312 includes, for example, a kernel 314,services 316, and drivers 322. The kernel 314 acts as an abstractionlayer between the hardware and the other software layers. For example,the kernel 314 provides memory management, Processor management (e.g.,task scheduling), component management, networking, and securitysettings, among other functionality. The services 316 can provide othercommon services for the other software layers. The drivers 322 areresponsible for controlling or interfacing with the underlying hardware.For instance, the drivers 322 can include display drivers, cameradrivers, BLUETOOTH® or BLUETOOTH® Low Energy drivers, flash memorydrivers, serial communication drivers (e.g., Universal Serial Bus (USB)drivers), WI-FI® drivers, audio drivers, power management drivers, andso forth.

The libraries 310 provide a low-level common infrastructure used by theSIPV applications 306. The libraries 310 can include system libraries318 (e.g., C standard library) that provide functions such as memoryallocation functions, string manipulation functions, mathematicfunctions, and the like. In addition, the libraries 310 can include APIlibraries 324 such as media libraries (e.g., libraries to supportpresentation and manipulation of various media formats such as MovingPicture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC),Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC),Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group(JPEG or JPG), or Portable Network Graphics (PNG)), graphics libraries(e.g., an OpenGL framework used to render in two dimensions (2D) andthree dimensions (3D) in a graphic content on a display), databaselibraries (e.g., SQLite to provide various relational databasefunctions), web libraries (e.g., WebKit to provide web browsingfunctionality), and the like. The libraries 310 can also include a widevariety of other libraries 328 to provide many other APIs to the SIPVapplications 306.

The frameworks 308 provide a high-level common infrastructure that isused by the SIPV applications 306. For example, the frameworks 308provide various graphical user interface (GUI) functions to the display,high-level resource management, and high-level location services. Theframeworks 308 can provide a broad spectrum of other APIs that can beused by the SIPV applications 306, some of which may be specific to aparticular operating system or platform.

In an example embodiment, the SIPV applications 306 used or integratedby the SIPV system 500 may include a rental application 336, a relatedservices application 330 (accessing other services related to the SIPV700 rental, a browser application 332, a user proximity application 334an alerting function to suggest nearby points of interest, road hazards,or other alters proximate to the user's location, a GPS application 342,a media application 344, a SIPV messaging application 346, a cameraapplication 348, and a broad assortment of other applications such as athird-party application 340 that would also service a related aspect ofthe present solution. The SIPV applications 306 are programs thatexecute functions defined in the programs and as listed throughout thisdescription. Various programming languages can be employed to create oneor more of the SIPV applications 306, structured in a variety ofmanners, such as object-oriented programming languages (e.g.,Objective-C, Java, or C++) or procedural programming languages (e.g., Cor assembly language). In a specific example, the third-partyapplication 340 (e.g., an application developed using the ANDROID™ orIOS™ software development kit (SDK) by an entity other than the vendorof the particular platform) may be mobile software running on a mobileoperating system such as IOS™, ANDROID™, WINDOWS® Phone, or anothermobile operating system. In this example, the third-party application340 can invoke the API calls 350 provided by the operating system 312 tofacilitate functionality described herein.

FIG. 4 is a diagrammatic representation of the SIPV computing machine400 within which instructions 410 (e.g., software, a program, anapplication, an applet, an app, or other executable code) for causingthe SIPV computing machine 400 to perform any one or more of themethodologies discussed herein may be executed. For example, theinstructions 410 may cause the SIPV computing machine 400 to execute anyone or more of the methods described herein. The instructions 410transform the general, non-programmed SIPV computing machine 400 into aparticular SIPV computing machine 400 programmed to carry out thedescribed and illustrated functions and operations in the mannerdescribed. The SIPV computing machine 400 may operate as a standalonedevice or may be coupled (e.g., networked) to other machines. In anetworked deployment, the SIPV computing machine 400 may operate in thecapacity of a server machine or a client machine in a server-clientnetwork environment, or as a peer machine in a peer-to-peer (ordistributed) network environment. The SIPV computing machine 400 maycomprise, but not be limited to, a server computer, a client computer,an onboard computer 808, a mobile device, a wearable device (e.g., asmart watch), a smart home device (e.g., a smart appliance), other smartdevices, a web appliance, a network router, a network switch, a networkbridge, or any machine capable of executing the instructions 410,sequentially or otherwise, that specify actions to be taken by the SIPVcomputing machine 400. Further, while only a single SIPV computingmachine 400 is illustrated, the term “machine” shall also be taken toinclude a collection of machines that individually or jointly executethe instructions 410 to perform any one or more of the methodologiesdiscussed herein.

The SIPV computing machine 400 may include Processor 408, memory 406,and SIPV I/O components 402, which may be configured to communicate witheach other via a bus 440. In an example embodiment, the Processor 408(e.g., a Central Processing Unit (CPU), a Reduced Instruction SetComputing (RISC) Processor, a Complex Instruction Set Computing (CISC)Processor, a Graphics Processing Unit (GPU), a Digital Signal Processor(DSP), an ASIC, a Radio-Frequency Integrated Circuit (RFIC), anotherProcessor, or any suitable combination thereof) may include, forexample, a Processor 412 and a Processor 408) that execute theinstructions 410. The term “Processor” is intended to include multi-coreprocessors that may comprise two or more independent processors(sometimes referred to as “cores”) that may execute instructionscontemporaneously. Although FIG. 4 shows multiple Processor 408, theSIPV computing machine 400 may include a single Processor with a singlecore, a single Processor with multiple cores (e.g., a multi-coreProcessor), multiple processors with a single core, multiple processorswith multiples cores, or any combination thereof.

The memory 406 includes a main memory 414, a static memory 416, and astorage unit 418, all accessible to the Processor 408 via the bus 440.The main memory 414, the static memory 416, and storage unit 418 storethe instructions 410 embodying any one or more of the methodologies orfunctions described herein. The instructions 410 may also reside,completely or partially, within the main memory 414, within the staticmemory 416, within machine-readable medium 420 within the storage unit418, within at least one of the processors 404 (e.g., within theProcessor's cache memory), or any suitable combination thereof, duringexecution thereof by the SIPV computing machine 400.

The SIPV I/O components 402 may include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific SIPVI/O components 402 that are included in a particular machine will dependon the type of machine. For example, portable machines such as mobilephones may include a touch input device or other such input mechanisms,while a headless server machine will likely not include such a touchinput device. It will be appreciated that the SIPV I/O components 402may include many other components that are not shown in FIG. 4. Invarious example embodiments, the SIPV I/O components 402 may includeoutput components 426 and input components 428. The output components426 may include visual components (e.g., a display such as a display, alight emitting diode (LED) display light 728), acoustic components(e.g., speakers, alerts like horns or other SIPV sounds), hapticcomponents (e.g., a vibratory motor, resistance mechanisms like brake730 actions), other signal generators, and so forth. The inputcomponents 428 may include alphanumeric input components (e.g., akeyboard, a touch screen configured to receive alphanumeric input, aphoto-optical keyboard, or other alphanumeric input components),point-based input components (e.g., a mouse, a touchpad, a trackball, ajoystick, a motion sensor, or another pointing instrument), tactileinput components (e.g., a physical button, a touch screen that provideslocation and/or force of touches or touch gestures, or other tactileinput components), audio input components (e.g., a microphone), and thelike.

In further example embodiments, the SIPV I/O components 402 may includeuser biometric components 430, 3D motion components 432, sensedenvironmental components 434, or navigation position components 436,among a wide array of other components. For example, the biometriccomponents 430 include components to detect expressions (e.g., handexpressions, facial expressions, vocal expressions, body gestures, oreye-tracking), measure biosignals (e.g., blood pressure, heart rate,body temperature, perspiration, or brain waves), identify a person(e.g., voice identification, retinal identification, facialidentification, fingerprint identification, orelectroencephalogram-based identification), and the like. The 3D motioncomponents 432 include acceleration sensor components (e.g.,accelerometer), gravitation sensor components, rotation sensorcomponents (e.g., gyroscope). The sensed environmental components 434include, for example, one or cameras, illumination sensor components(e.g., photometer), temperature sensor components (e.g., one or morethermo-sensors that detect ambient temperature), humidity sensorcomponents, pressure sensor components (e.g., barometer), acousticsensor components (e.g., one or more microphones that detect backgroundnoise), proximity sensor components (e.g., infrared sensors that detectnearby objects), gas sensors (e.g., gas detection sensors to detectionconcentrations of hazardous gases for safety or to measure pollutants inthe atmosphere), or other components that may provide indications,measurements, or signals corresponding to a surrounding physicalenvironment. The navigation position components 436 include locationsensor components (e.g., a GPS receiver Component), altitude sensorcomponents (e.g., altimeters or barometers that detect air pressure fromwhich altitude may be derived), orientation sensor components (e.g.,magnetometers), and the like.

Communication may be implemented using a wide variety of technologies.The SIPV I/O components 402 further include communication components 438operable to couple the SIPV computing machine 400 to a network 422 ordevices 424 via respective coupling or connections. For example, thecommunication components 438 may include a network interface Componentor another suitable device to interface with the network 1422. Infurther examples, the communication components 438 may include wiredcommunication components, wireless communication components, cellularcommunication components, Near Field Communication (NFC) components,Bluetooth® components (e.g., Bluetooth® Low Energy), WiFi® components,and other communication components to provide communication via othermodalities. The devices 424 may be another machine or any of a widevariety of peripheral devices (e.g., a peripheral device coupled via aUSB).

Moreover, the communication components 438 may detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 438 may include Radio Frequency Identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as Universal Product Code (UPC) bar code,multi-dimensional bar codes such as Quick Response (QR) code, Azteccode, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2Dbar code, and other optical codes), or acoustic detection components(e.g., microphones to identify tagged audio signals). In addition, avariety of information may be derived via the communication components438, such as location via Internet Protocol (IP) geolocation, locationvia Wi-Fi® signal triangulation, location via detecting an NFC beaconsignal that may indicate a particular location, and so forth.

The various memories (e.g., main memory 414, static memory 416, and/ormemory of the Processor 408) and/or storage unit 418 may store one ormore sets of instructions and data structures (e.g., software) embodyingor used by any one or more of the methodologies or functions describedherein. These instructions (e.g., the instructions 410, when executed byprocessors 404, cause various operations to implement the disclosedembodiments.

The instructions 410 may be transmitted or received over the network422, using a transmission medium, via a network interface device (e.g.,a network interface Component included in the communication components438) and using any one of several well-known transfer protocols (e.g.,hypertext transfer protocol (HTTP)). Similarly, the instructions 410 maybe transmitted or received using a transmission medium via a coupling(e.g., a peer-to-peer coupling) to the devices 424.

SIPV System Network Overview:

SIPV system 500 as functionally presented can also be characterized asapart of a network of SIPVs 100 s interconnected via several networktypes comprising cloud, cellular, wireless, mesh or CAN bus networkeither using Virtual Machines or other Processor hardware to create asystem grouping. Several network types of controllers maybe used in thissolution comprising individual or hybridized networks as describedearlier One variant of the present solution further comprises a MeshedSIPV Network 600 bus as shown in FIG. 6, and another is the CAN busprotocol discussed here. The Can bus is one of these central networkingprotocols used in vehicle systems without a host computer. The CAN Busin this solution is an International Standardization Organization (ISO)defined serial communications bus originally developed for theautomotive industry to replace the complex wiring harness with atwo-wire bus. The specification calls for high immunity to electricalinterference and the ability to self-diagnose and repair data errors.These features have led to CAN's popularity in a variety of industriesincluding building automation, medical, and manufacturing. The CANcommunications protocol, ISO-11898: 2003, describes how information ispassed between devices on a network and conforms to the Open SystemsInterconnection (OSI) model that is defined in terms of layers. Actualcommunication between devices connected by the physical medium isdefined by the physical layer of the model. The ISO 11898 architecturedefines the lowest two layers of the seven layer OSI/ISO model as thedata-link layer and physical layer. By connecting all the modules in avehicle to one central line, the control system is simplified and moreeasily regulated. This design allows any connected Module to alert themain controller to an event that as it occurs which will cause the restof the system to respond accordingly. The shared data line allowsmultiple modules to be attached with less invasive efforts, making thepotential for error much lower. If one Module on the CAN bus fails, itdoes not necessarily cause the failure of other modules. Unless the twosystems are directly related, and one cannot run without the other, thehealthy modules will continue to function perfectly despite the loss ofone bad Module. This makes the entire system safer. Additionally,diagnostics of the SIPV 700 are simpler and more specific due to thespecialized and self-contained nature of the modules. Diagnostics cannow pinpoint the exact cause of the Module failure with accuracy andspeed. When one Module needs maintenance, that Module can simply betargeted and replaced rather than tearing apart the entire vehicle. CANbus offer a simple interface for attaching an additional nodes in thepresent solution. Each of the nodes can be used for diagnostics,reprogramming, monitoring, and more. The utility of these Module nodescan be seen in the SIPV system 500. SIPV 700 comprising at least anintegrated safety control apparatus 504 wherein the integrated safetycontrol apparatus 504 polls a sensor suite 506 further comprisingplurality of sensors measured data parameters of the present SIPV thatare selected from a group of tire pressure, seat occupancy, helmet worn,helmet missing, speedometer, accelerometer, GPS location, image capture,video streamed, user input commands, bump detection, SIPV pitch/roll/yaworientation, battery status, motor status, rental status)from thecurrently active SIPV 700. This plurality of data is converted by theintegrated safety control apparatus 504 into parameters related to safeuse by a rider, a communication link to a SIPV safety controller 510 totransmit the parameters related to safe use by a rider on a SIPV, and atleast an instruction received from the SIPV safety controller 510 viathe communication link to direct a plurality of control units controlledin the SIPV physical controls suite 512 to modify current operationparameters (e.g. Applying a brake, reducing acceleration, cutting power,actuating signals and tones in the SIPV 700 (e.g. commanding compliancevia the display) in a manner to bring the SIPV back to a safe use. TheSIPV system 500 may also take over and slave the SIPV controller 502 ifthe data received from the present SIPV warrants the use of a redundantcontrol of the SIPV. For clarity, the SIPV controller 502 may alsoreside externally to the SIPV 700 in this solution as well. As furtherdemonstrated in FIG. 7 the SIPV system 500 further comprises a VendingModule 514, which handles authentication of a user, the validation ofthe payment method provided, provision of authorization for the userrental of a SIPV 700; an Operation Module 516 which handles theoperational monitoring and control of the SIPVs managed by the SIPVsystem 500 and manages the activation or disabling commands of SIPV 700that are under its control. The Maintenance Module 518 also managesmaintenance requests by/to specific SIPV 700 that allow a maintenanceteam to be dispatched for servicing or power source replacement. TheAnalytics Module 520 collects, aggregates and presents data from theSIPVs to help those managing the SIPV system 500 optimize theirOperation Module 516 with SIPV 700 placement and usage.

Mesh Network:

A mesh network (or simply mesh-net) as shown in FIG. 6 is a localnetwork topology in which the infrastructure nodes (i.e. bridges,switches and other infrastructure devices) connect directly, dynamicallyand non-hierarchically to as many other nodes as possible and cooperatewith one another to efficiently route data from/to clients. This lack ofdependency on one node allows for every node to participate in the relayof information. Mesh networks dynamically self-organize andself-configure, which can reduce installation overhead. The ability toself-configure enables dynamic distribution of workloads, particularlyin the event that a few nodes should fail. This in turn contributes tofault-tolerance and reduced maintenance costs. Mesh topology may becontrasted with conventional star/tree local network topologies in whichthe bridges/switches are directly linked to only a small subset of otherbridges/switches, and the links between these infrastructure neighborsare hierarchical. The Meshed SIPV Network 600 comprises a meshed SIPVsystem 802, that is operably connected with a wireless network 604 asdisclosed above, the Meshed SIPV Network 600 in operable communicationwith at least one device(a user cell phone 606, or a User computingdevice 608) the meshed SIPV system 602 delegating operations, monitoringor other computing tasks to at least a meshed SIPV controller 610. Themeshed SIPV controller 610 then in operable communication with at leasta meshed SIPV 612. The meshed SIPV 612 is also in operablecommunications with other meshed SIPV 612 as well other meshed SIPVcontroller 610 if the working area of a meshed SIPV system 602 is largerthan the practical range of a single mesh meshed SIPV controller 610. Auseful configuration of a meshed SIPV 612 interaction would be to useidle meshed SIPV 612 for computing power as they are out of service.Additionally, active in-use meshed SIPV 612 should be aware of andmonitoring other meshed SIPV 612 around their communication area to helpco-locate the meshed SIPV 612 of interest. Additionally, integrationwith the user cell phone 606 and the wireless network 604 to continue toassist in triangulation problems where a particular meshed SIPV 612 waslast connected. For the sake of clarity, the use of wireless network 604and user cell phone 606 would work in the other network types used inthe present solution, it is not intended that this functionalilty onlyexist in the Meshed SIPV Network 600 example.

The safety enabled personal mobility vehicle or safety integratedelectrically powered vehicle SIPV 700 shown in FIG. 7 comprises asubstantially rigid frame with at least two wheels 704 mounted to theframe supporting a seat 708 for at least a single user of the SIPV 700and an articulated steering column mounted to at least one of thewheels. The wheel 704 further comprising a wheel hub 716 spokes 718, awheel rim 720 and tire 706, the wheel in front being rotatablyarticulated for steering with the articulated steering column furthercomprising a set extending at a substantially perpendicular orientationfrom the articulated steering column with each handle set at a heightfor a user to steer the SIPV 700 while riding the SIPV 700. The SIPV mayhave several configurations for a user, sitting or standing on the SIPV700, FIG. 7 depicts a seated version. The set of handles 710 includes anacceleration control 714 and a braking control 712 operably connected tothe wheel hub 716 that houses a brake 730 in at least one or more of thewheels. The frame further comprises foot rests 722, light 728, a driveapparatus 732 operably connected to the acceleration control thatpropels the wheels (e.g., via a gear set or direct drive), a powersource interface, and a mobile computing Processor hardware Although notillustrated in FIG. 7, the SIPV 700 can also include other componentsthat are integrated into the SIPV 700. (e.g. Camera, a Accelerometer, apower source among other sensors)

The frame can vary depending on the implementation, and can befabricated using a number of materials. In this variant of the solutionin FIG. 7, the frame has a open design to ensure that the SIPV 700 iscompatible with all types of clothing. The frame allows for acomfortable upright riding position allowing the rider to sit on seat708, resting on foot rests 722 and allowing the SIPV 700 to be parked ona kickstand 724 The drive apparatus 732 is located in this version ofthe solution in the back wheel hub 716. A safety linkage 736 iswirelessly connected to the Safety device 738 to link it to the SIPV 700to allow the SIPV 700 to enforce the use of a Safety device 738. For thesake of clarity, this variant of the solution focuses on use of a helmetas a Safety device 738 however the solution contemplates dispensation ordeployment of other safety device types as well(e.g. Debris protection,other joint protection as well as rash protection devices)

The tire on wheel 704 can be made from a solid or puncture resistantmaterial. The wheels are secured to the frame using standard components(e.g., nuts). In general, the SIPV 700 can be made from unique parts(e.g., nuts and screws) having sizes to help deter theft. For instance,the nuts and screws that are part of the SIPV 700 can be designed suchthat they can only be opened with proprietary interfaces furthercomprising electronic locks (e.g. BlueTooth® interfaces as describedlater in this description).

The wheel hub 716 house the brake 730 and/or drive apparatus 732. Theinternal wheel hub 716 can keep the wiring for brakes and gears enclosedand hidden. The brake 730 can include front and rear drum brakesoperably connected to the set of handles 712 and the accelerationcontrol operably attached for the drive apparatus 732 Other types ofbrakes such as disk, cantilever, and V-brakes may also be used.

The light 728 can further comprise at least a multiple LED lightspowered by the power source mounted internally in the seat post 726. Thepower source 902 will be introduced later in FIG. 9. The light 728 canbe replicated anywhere on the SIPV 700 to help provide visibility atnight. In addition, lighted or reflective surfaces can also be appliedto Logo zones on wheels, pedals, and on other visible areas of the SIPV700 to enhance the solution branding and safety. An example of thisfeature is the power indicator 734 in FIG. 7 where a logo doubles as apower indicator 734

The seat post 726 can also be an adjustable height that allows theheight of the seat 708 to be adjusted. The quick release feature of theseat post 726 is designed to allow easy height adjustments withoutmaking it possible to completely remove the post. A numbering system onthe seat post 726 can help frequent users adjust the height of the seat708 quickly to the pre-set height that the rider desires.

A significant aspect of this solution is that many of the safetyfeatures are built in and integrated at the SIPV 700 level, the SIPVsystem 500 level and extended to the user of the SIPV before, during andafter the ride.

In FIG. 8, the handle further comprising a mounting for an accelerationcontrol, a braking control, a display of SIPV 700's (BLE, cell, WiFi)network connections, status, location, other informatics, displayingdata received from an onboard computer 808 (functionality furtherdescribed in FIG. 9 and FIG. 7 mounted beneath the display, or down inthe frame (the second option is shown in FIG. 9), turn signal control804 and an antenna 806 for communication to the SIPV system 500 asintroduced in FIG. 5. Turn signal control 804 is also linked to light728 to indicate SIPV 700 turning by the user. Another aspect of thesolution shown is rider authentication apparatus rider authenticationapparatus 810 which is shown on as a QR code symbol in the writtendescription, but could be accomplished with RFID technology, Bluetooth,Near Field Communications, or other device pairing technologies to allowa user to quickly authenticate and purchase a ride on the SIPV 700

In FIG. 7. shows an exploded view of the SIPV 700 is shown thesubstantially rigid frame further comprising: a power source powering adrive apparatus further comprising: at least a drive apparatus drivingat least one of the wheels; a rider authentication apparatus 810; anacceleration control linkage to the drive apparatus for starting,maintaining, and decreasing movement of the SIPV 700 responsive tocommands from a user input from the handle mounted controls(712 or 714)or from a SIPV system 500 or the onboard computer 808 to correct adetected unsafe condition. The drive apparatus is further comprising amotor, a power linkage to the power source and mechanical linkage to thewheel that the drive apparatus is driving. For the sake of clarity, themotor may directly drive the wheel 704 or indirectly drive the wheel 704via chain/sprocket/drive shaft/transmission/or other indirect drivemethods.

In FIG. 8, a close up of the control surfaces of the SIPV system 500 isalso operably linked to a brake 730, the drive apparatus or the energypower source; a control linked to light 728 for signaling vehicle turnsor braking (light 728 includes locations on the back and sides of theSIPV 700 for the sake of clarity). This SIPV system 500 linkage is inaddition to inputs from the a user input from the handle brake controlor a turn signal control 804 is fully coupled to the brake or turnindicator, respectively. The SIPV 700 wirelessly coupling to a Safetydevice 738 (e.g. a helmet) connected to the SIPV 700 to monitor for usersafety further connected to the SIPV system 500 for transmission ofother safety related data. The safety data that is interwoven into thesafety solution comprises: Tire pressure used to detect safe drivingconditions as well as safe loads (i.e. more riders than SIPV 700 is ableto handle. A Seat sensor 1002 interlinked with the power source 808 toestablish that a user is in place on the seat 708. A Bump sensor 1004(both introduced in FIG. 10) allowing the SIPV 700 to identify unsafedriving (e.g., riding on sidewalks and other unsafe terrain. Othercombinations of tire pressure data, bump sensor working in conjunctionwith the speedometer can identify unsafe speed and loads on the rigidframe. The SIPV 700 roll, yaw and pitch as well as SIPV 700 angle andupright gyroscope data to estimate SIPV status, detect accidents orother impacts on the SIPV, detection of uphill travel to increase powerto drive apparatus, detection of downhill travel to establish systembraking or power recovery protocols to keep SIPV from exceeding safedecent speeds. Integration with accelerometer/speedometer data alsoprovides significant data for the SIPV 700 and SIPV system to detect,intervene if necessary, and transmit instructions to drive motor andbraking performance. Servicing protocols are extracted from motor, brakeand power sources. (e.g., the power source reports its charge status andusage. Although not explicitly a sensor, speakers/horns, displays andhead lights/signal/telltale lights all are used to cue the rider ofsafety issues, warning the rider visually, aurally, or haptic notice ofa safety issue. Finally, in the variants of this solution where at leasta camera/video device is mounted in the SIPV 700, such that the visualdetection of surroundings or items is also integrated into a safetyscenario and forensic event recording. The camera can be uses to collectride surroundings on a continuous basis to create the equivalence of aflight recorder and stream ride data to the SIPV system 500 during aride for diagnostic purposes.

For the sake of clarity, the SIPV 700 comprises electric bicycles,electric mopeds, electric scooters and can further comprise any/allelectric mobility vehicles having up to three wheels that are powered byan electric motor and primarily get their energy from the power grid—inother words: an EV that can be recharged or powered externally. Thisincludes purely electric vehicles, vehicles that assist human power withelectrical power assistance (e.g. pedaled), vehicles with a combinationof electric motor and a small combustion engine (range extended electricvehicles—REEV), and hybrid vehicles that can be recharge via the powergrid (plug-in hybrid electric vehicles—PHEV).

In FIG. 9, a cross-sectional view of the SIPV 700 further comprises apower source 902 that allows a rapid replacement by service personnelfurther comprising with safety and security interlocks that keep theSIPV 700 safer from vandalism and other threats. The power source 902uses the Seat sensor 1002 that interacts with the SIPV 700 to determineif a rider is present on the seat 708 prior to the ride on the SIPV 700allowing the drive apparatus to be engaged. Power source as defined inthis solution includes electrical storage devices like batteries oractive electrical generation devices like fuel cells that provide anelectrochemical cell that converts the chemical energy of a fuel (oftenhydrogen) and an oxidizing agent (often oxygen) into electricity througha pair of redox reactions.

As shown in FIG. 10, the exploded view of the SIPV 700 showing the SeatSensor 1002 and the Bump Sensor 1004 locations on the SIPV 700 aspreviously introduced.

As shown in FIG. 11, a power source 902 having compatible dimensions forseating inside a SIPV seat post 726 is inserted into of the SIPV 700with the power source connector end 1102 of the power source 902inserted first. A solenoid latch 1104 is pressed out of the way as thepower source 902 is inserted into the seat post 726 and then thesolenoid latch 1104 then re-extends once the power source 902 is fullyinserted, locking the power source 902 into the seat post 726 When thepower source 902 is fully inserted into the seat post 726, the powersource connector end 1102 engages with the power source connectorreceptacle 1106 located at the bottom of the seat post 726. Once thepower source connector receptacle 1106 connected with the power sourceconnector end 1102, the power source powers the SIPV 700 and itsrespective vehicle control and authentication systems control(712,714,810,) thereby allowing Bluetooth Low Energy or the equivalentcommunications with the (SIPV 700 or the SIPV system 500) and theonboard computer 808 enabling control of the solenoid latch 1104.Servicing of the power source 902 is then enabled allowing the solenoidlatch 1104 to be triggered by a mobile device application via BluetoothLow Energy (BLE) link with solenoid latch 1104. Once unlatched, thepower source 902 is removable. The SIPV system 500 can also trigger thesolenoid latch 1104. Using the mobile device application, a maintenancecommand to unlock and remove the power source 902 is sent via BLE to theonboard computer 808 that issues a command to the solenoid latch 1104via a digital bus. This digital bus can be a CAN bus or UART or otherdigital bus formats. As mentioned above, the power source 902 furthercomprises a Seat sensor 1002 comprising an integrated force-sensitiveresistor drive circuit or its equivalent, which allows detecting thepresence of a seated rider. Additionally, the power source 902 can alsoreceive a deactivate command via BLE from a service technician, the SIPVsystem 500 or the onboard computer 808 if a disable requirement exists.(e.g., SIPV is stolen or damaged)

The present solution power source 902 provides for mass servicing, wherethe maintenance mobile device can simultaneously unlock multiplesolenoid latch 1104 on multiple SIPV 700 via BLE. In the event of apower source 902 being drained and the solenoid latch 1104 is in anunpowered state, the power source 902 further comprises a power accessport that enables a technician to power the solenoid latch 1104 andallow the removal of the power source 902. Additional safetyconsiderations in the present invention's power configurations furthercomprise keeping the SIPV drive apparatus unpowered until a power-upprocedure dictated by the onboard computer 808 is followed including useof the Safety device 738. The power source 902 further comprises adigital displayed of remaining capacity that is displayed either at thepower indicator 734 or on the display. The power source 902 can bepopulated with a variable number of power cells/fuel cells to saveweight and cost, or to comply with local regulations.

FIG. 12 displays a variant of the Safety device 738 and a SIPV mountingapparatus as it would be mounted on a SIPV 700. There are many placesthe safety device can be mounted on a SIPV 700 and the various variantsof this solution are largely due to aesthetics. This variant of thesolution's Safety device 738 deployment features a Mounting Clip 1202where the Safety device 738 has a number of clip indents where theSafety device 738 has a Safety Device Retention Slot 1210 that fit witha Safety device retainer 1204 as the Safety device 738 is placed intothe base of Mounting Clip 1202 and placed up into positions such thatthe Safety device retainer 1204 can be moved into position where theLatching Module 1206 will actuate to lock the device into place. Thelatching Module further comprises a local wireless connection to theonboard computer 808 and reports out that the latch is closed as well asconfirming a near distance link between a Safety device sensor 1208mounted in the Safety device 738 and a Mounting latch sensor 1212located in the Latching Module 1206. One variant of this solution wouldcarry permanent magnets to create a magnetic field that hall sensorsemplaced in the Safety device 738 can use to detect a helmet presence.There are a number of variations of this configuration, but the basicaspect of the deployable Safety device 738 is that it is contained inthe SIPV 700 and is deployed when the ride is purchased and recovered tothe SIPV 700 and verified retrieved to the SIPV system 500. Thedeployment of this Safety device 738 typically is deployed once a userorders a SIPV 700 ride using a user mobile device. Upon validation ofpayment, the Latching Module 1206 receiving an unlocking command fromonboard computer 808 or from the user mobile device if an app is used togenerate an unlocking command. The solution contemplates eitherunlocking/retrieval methodology.

A typical SIPV rental process is outlined in FIG. 13, The SIPV rentalprocess comprises a Start SIPV Rental 1302 step, where a particular SIPV700 is identified for a rental. The user wanting to ride that SIPV 700makes a Ride request step via mobile device/computing device of userstep 904. where a potential user would use their mobile device to rent aparticular SIPV 700(e.g, by using a QR code or an app that accomplishesthe same usage), Selection of Destination 1308 is made after the usermakes a Review ride destinations 1306 step. In the alternative, the usercan simply rent the SIPV without selecting a destination and the SIPVwill simply limit the ride to general service area). Once a Selection ofDestination 1308 step has been made, the user will finalize the step ofBook the SIPV 1312, which further comprises aa Payment Authorization1314, and then to ultimately an Exit Transaction 1316 step. This bookingstep will in turn cause the Deploy Safety Device 1318 step releasing aSafety device 738 to the renting user, the SIPV 700 will validate thatthe Safety device 738 is working and in place completing a Safety DeviceWorking and Used 1320 step. If the user does not use the Safety device738 and it is permitted by law, a Wavier of Liability 1322 step isinitiated, requiring the user to return the Safety device 738 to theLatching Module 1206. Once the Safety device 738 is restowed and latchedinto place, the waiver can be signed by the user and finalized to bringthe SIPV ride ready at the Finish SIPV rental 1324 step.

The Safe Ride Flowchart 1400 is shown in FIG. 14 comprises a ContinueRide 1402 step where a user begins a ride on the SIPV 700 and thevarious safety systems support the ride with ongoing monitoring, aMonitor SIPV progress 1404 step simply monitors the ride and comparesany known parameters for the ride. If the SIPV is on an On Correct Route1406 step and no other safety alerts are generate, the SIPV takes noactions, gives no alerts until the SIPV 700 arrives at an At Destination1408 step, and a final position of the SIPV 700 is established and alsowhere recovery of the Safety device 738 begins. During a Recover SafetyDevice 1410 step, the user is prompted to remove a liner inside theSafety device 738 and to return it to the Safety device retainer 1204and to lock the Safety device 738 into the mounting clip and to lock it.The SIPV broadcasts a recovery signal to the SIPV system 500 and theSIPV validates that a Safety Device Recovered 1412 step has beencompleted. After that step, a Finalize Transaction 1414 step iscompleted, the final Payment Authorization 1314 is completed, and theride is over. However, if a user is using the SIPV unsafely, anotherprocess loop initiates which causes a Route Correction 1416 step to begenerated once the SIPV 700 moves off a target area serviced by the SIPVsystem 500. In addition to this step, a number of other warnings can beoffered (e.g. an overweight ride, illegal sidewalk riding, driving downone-way streets backwards, and other SIPV 700 riding behaviors that theSIPV system 500 wishes to prohibit.) The SIPV 700 then pushes out, anOffer Advisory Warning 1418 step that gives that user a warning toreturn to an approved route or local or suffer a disabled SIPV 700. Oncea warning has been ignored, a Disable Vehicle 1420 step is engaged. Oncethe Vehicle has been disengaged, a Notify SIPV servicing 1422, step ismade telling the servicing team to go retrieve a SIPV 700 and return theonboard computer 808 to a Rental 1124 state.

Bluetooth Usage

The present solution uses Bluetooth to interact and pair a user to aparticular shared ride rental and the user's mobile device. Bluetooth isa popular standard for close-range wireless communication. It providesthe ability to pair two devices together and thereby exchangeinformation with each other. An example of the authentication mechanismutilized by Bluetooth devices is described below. The pairing process,also known as the standard pairing, requires the two devices (usermobile device and the SIPV 700) establish an initial symmetric key inorder to communicate securely. In this case there are two devices, auser mobile device and SIPV 700 being rented. The two devices at firsthandle two keys, share a PIN and know each other's 48-bit Bluetoothdevice address (BD_Addr). The first key is the symmetric initializationkey (Kinit) to mutually authenticate each other and the second is a linkkey. The link key is generated during the pairing session with the helpof the initialization key. The ‘Unit key’ is generated when the deviceis first operated with the help of the key generation algorithm. The‘Initialization key’ is needed when two devices need to communicate witheach other. It is used for exchanging link keys and for encryption aswell as decryption of information during the link key generationprotocol. The ‘Link key’ can be used in two different methods. Thedevices' unit key can be sent with encryption of the initialization keyand this would constitute a link key or the device can generate a randomnumber and then send it under the encryption of the initialization keyand thereby generate a link key. The ‘Combination key’ is generatedduring the Initialization process at the same time and is only valid forthe session only. This key is exchanged when the two devices computetheir link keys. It comprises of a 128 bit random number and theBluetooth device address. The ‘Encryption key’ is generated from thecurrent link key during the authentication process. It is based on theCOF (96 bit Ciphering Offset Number). The ‘Master key’ is generally usedas the link key if the master needs to transmit to multiple slaves. Itis generated using the key generation algorithm by virtue of the 128 bitrandom number. The resultant link key is then sent to the slave, bitwisexored with overlay. With this, slave can compute master key.

Bluetooth Pairing Mechanism

At the onset, both the devices share a low-entropy human-readable secretPIN. Typically the PIN comprises of a 4-digit code, which can be up to128 bits When device 1 initiates the connection it is referred to as theinitiating device and it does so by generating a random nonce (numberused once) n1, and then sending it to device 2. Both devices thencompute a shared initialization key Kinit using the E22 algorithm. Thekey Kinit is a function of n1, BD_Addr1, and PIN.

Device Authentication

After the shared key generation, the two devices authenticate each otherbefore generating the encryption key. It is based on the challengeresponse scheme. The verifier (device 2) sends a plain-text random valueAV_RAND2, the receiver (device 1) then computes a response SRES=E1(Kinit, BD_Addr1, AV_RAND2) where E1 is the algorithm. The verifierperforms the same calculation and compares the response to the verifier.After the verification, a match is required for the mutualauthentication process to be successful.

Bluetooth Encryption

The Bluetooth mechanism involves the use of block cipher algorithm forencryption and Link Key generation. Further, the encryption of packetsis performed using a stream cipher and 4 linear feedback shiftregisters. After authentication, a cipher key K3 is generated. The keylength is 128 bits to ensure high level of security. After the key isgenerated, the data payload is encrypted using the cipher stream engineE0 and takes as inputs the encryption key, BD_Addr, 128 bit randomnumber and the 26 LSB of the master's clock. The input values areshifted into four linear feedback shift registers and then combined inthe summation combiner FSM to produce the cipher. This generates a newcipher every time.

The above description includes references to the accompanying drawings,which form a part of the detailed description. The drawings show, by wayof illustration, specific embodiments in which the invention can bepracticed. These embodiments are also referred to herein as “examples.”Such examples can include elements in addition to those shown ordescribed. However, the present inventors also contemplate examples inwhich only those elements shown or described are provided. Moreover, thepresent inventors also contemplate examples using any combination orpermutation of those elements shown or described (or one or more aspectsthereof), either with respect to a particular example (or one or moreaspects thereof), or with respect to other examples (or one or moreaspects thereof) shown or described herein.

In the event of inconsistent usages between this document and anydocuments so incorporated by reference, the usage in this documentcontrols.

In this document, the terms “a” or “an” are used, as is common in patentdocuments, to include one or more than one, independent of any otherinstances or usages of “at least one” or “one or more.” In thisdocument, the term “or” is used to refer to a nonexclusive or, such that“A or B” includes “A but not B,” “B but not A,” and “A and B,” unlessotherwise indicated. In this document, the terms “including” and “inwhich” are used as the plain-English equivalents of the respective terms“comprising” and “wherein.” Also, in the following claims, the terms“including” and “comprising” are open-ended, that is, a system, device,article, composition, formulation, or process that includes elements inaddition to those listed after such a term in a claim are still deemedto fall within the scope of that claim. Moreover, in the followingclaims, the terms “first,” “second,” and “third,” etc. are used merelyas labels, and are not intended to impose numerical requirements ontheir objects.

Geometric terms, such as “parallel”, “perpendicular”, “round”, or“square”, are not intended to require absolute mathematical precision,unless the context indicates otherwise. Instead, such geometric termsallow for variations due to manufacturing or equivalent functions. Forexample, if an element is described as “round” or “generally round,” acomponent that is not precisely circular (e.g., one that is slightlyoblong or is a many-sided polygon) is still encompassed by thisdescription.

Method examples described herein can be machine or computer-implementedat least in part. Some examples can include a Computer-Readable Mediumor machine-readable medium encoded with instructions operable toconfigure an electronic device to perform methods as described in theabove examples. An implementation of such methods can include code, suchas microcode, assembly language code, a higher-level language code, orthe like. Such code can include computer readable instructions forperforming various methods. The code may form portions of computerprogram products. Further, in an example, the code can be tangiblystored on one or more volatile, non-transitory, or non-volatile tangiblecomputer-readable media, such as during execution or at other times.Examples of these tangible computer-readable media can include, but arenot limited to, hard disks, removable magnetic disks, removable opticaldisks (e.g., compact disks and digital video disks), magnetic cassettes,memory cards or sticks, random access memories (RAMs), read onlymemories (ROMs), and the like.

The above description is intended to be illustrative, and notrestrictive. For example, the above-described examples (or one or moreaspects thereof) may be used in combination with each other. Otherembodiments can be used, such as by one of ordinary skill in the artupon reviewing the above description. The Abstract is provided to allowthe reader to quickly ascertain the nature of the technical disclosure.It is submitted with the understanding that it will not be used tointerpret or limit the scope or meaning of the claims. Also, in theabove Detailed Description, various features may be grouped together tostreamline the disclosure. This should not be interpreted as intendingthat an unclaimed disclosed feature is essential to any claim. Rather,inventive subject matter may lie in less than all features of aparticular disclosed embodiment. Thus, the following claims are herebyincorporated into the Detailed Description as examples or embodiments,with each claim standing on its own as a separate embodiment, and it iscontemplated that such embodiments can be combined with each other invarious combinations or permutations. The scope of the invention shouldbe determined with reference to the appended claims, along with the fullscope of equivalents to which such claims are entitled.

What is claimed is:
 1. A SIPV system comprising: a SIPV networkconnecting to at least a SIPV; the SIPV made available for rental; theSIPV comprising an integrated safety control apparatus in the SIPV; theintegrated safety control apparatus operably connected to a safetydevice mounted on the SIPV; and upon rental of the SIPV, the safetydevice is deployed for use from the SIPV.
 2. The SIPV system of claim 1wherein the safety device is operably connected to the SIPV while theSIPV is being used.
 3. The SIPV system of claim 1 further comprising asafety linkage between the SIPV power source and a presence on the seatsensor wherein the SIPV doesn't receive power until the seat sensorindicates a rider in place.
 4. The SIPV system of claim 1 furthercomprising a safety linkage between the safety device and the SIPVbraking control wherein the SIPV receives a confirmation of a safetydevice is in use in order to power the SIPV.
 5. The SIPV system of claim1 further comprising the SIPV system that polls a sensor suite availableon the SIPV to measure safety conditions of the ride.
 6. The SIPV systemof claim 5 wherein the sensor suite measures a plurality of sensors dataparameters of the in use SIPV as selected from a group of safety dataparameters (SIPV tire pressure, SIPV seat occupancy, SIPV safety deviceworn, SIPV safety device missing, SIPV speedometer readings, SIPVaccelerometer readings, SIPV GPS location, SIPV camera image capture,SIPV video streamed, SIPV bump detection, SIPV pitch/roll/yaworientation, SIPV current power source status, SIPV drive apparatusstatus, SIPV rental status).
 7. The SIPV system of claim 1 furthercomprising the SIPV system use of a communication link to issue a safetyalert to an in-use SIPV if a safety data parameter is outside a safetylimit.
 8. The SIPV system of claim 7 further comprising the SIPV use ofa communication link to disable an in-use SIPV if the safety alert isignored.
 9. The SIPV system of claim 1 further comprising the SIPVgenerates a request to return the safety device at the end of the SIPVrental back to its mount on SIPV.
 10. The SIPV system of claim 1 furthercomprising the SIPV generates a request to a display to remove a usedliner prior to return of the safety device.
 11. The SIPV system of claim1 further comprising the SIPV system validates the return of the safetydevice prior to the final charge associated with the rental of the SIPV.12. The SIPV system of claim 8 further comprising the removable safetydevice is a helmet operably connected to the SIPV to report helmetstatus.
 13. The SIPV system of claim 8 further comprising the helmetthat is sanitized by removal of a liner in the helmet.
 14. A shared ridemethod comprising: a SIPV system having a SIPV rental process; receivingthe SIPV rental request from a mobile device; authenticating atransaction allowing a rental of the SIPV; deploying a safety devicefrom the SIPV along with the rental of the SIPV; and requiring a riderto use the safety device before allowing movement of the SIPV.
 15. Theshared ride method of claim 14 further comprising a sensor linking thesafety device reporting the charge condition of the SIPV power source.16. The shared ride method of claim 14 further comprising linking to theSIPV network to report a set of ride data parameters corresponding tothe safe use of the SIPV.
 17. The shared ride method of claim 14 furthercomprising measuring safe usage by polling a sensor suite on the SIPV;and monitoring the set of data received by the sensor suite.
 18. Theshared ride method of claim 17, further comprising the SIPV safetycontroller directing the SIPV physical control suite to physicallycontrol the SIPV to a safer operating condition.
 19. The shared ridemethod of claim 14 further comprising transmitting SIPV power sourcecharge status to the SIPV network for initiating a maintenance call. 20.The shared ride method of claim 14 wherein the SIPV is requesting thereturn of the safety device at the end of the SIPV rental.
 21. Theshared ride method of claim 20 wherein the SIPV is requesting thesanitation of the safety device by removing a removable liner in thesafety device.